SGI Freeware 1999 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 1999 August / SGI Freeware 1999 August.iso / dist / fw_mtools.idb / usr / freeware / catman / u_man / cat5 / mtools.Z / mtools

Wrap

Text File | 1998-10-28 | 36.4 KB | 661 lines

MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) NNNNAAAAMMMMEEEE mtools - table of DOS devices DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN ////eeeettttcccc////mmmmttttoooooooollllssss....ccccoooonnnnffff and ~~~~////....mmmmttttoooooooollllssssrrrrcccc are the configuration files for mtools. These configuration file describes the following items: oooo GGGGlllloooobbbbaaaallll ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn ffffllllaaaaggggssss aaaannnndddd vvvvaaaarrrriiiiaaaabbbblllleeeessss oooo PPPPeeeerrrr ddddrrrriiiivvvveeee ffffllllaaaaggggssss aaaannnndddd vvvvaaaarrrriiiiaaaabbbblllleeeessss oooo CCCChhhhaaaarrrraaaacccctttteeeerrrr ttttrrrraaaannnnssssllllaaaattttiiiioooonnnn ttttaaaabbbblllleeeessss ////eeeettttcccc////mmmmttttoooooooollllssss....ccccoooonnnnffff is the system-wide configuration file, and ~~~~////....mmmmttttoooooooollllssssrrrrcccc is the user's private configuration file. GGGGeeeennnneeeerrrraaaallll SSSSyyyynnnnttttaaaaxxxx The configuration files is made up of sections. Each section starts with a keyword identifying the section followed by a colon. Then follow variable assignments and flags. Variable assignments take the following form: nnnnaaaammmmeeee====vvvvaaaalllluuuueeee Flags are lone keywords without an equal sign and value following them. A section either ends at the end of the file or where the next section begins. Lines starting with a hash (####) are comments. Newline characters are equivalent to whitespace (except where ending a comment). The configuration file is case insensitive, except for item enclosed in quotes (such as filenames). DDDDeeeeffffaaaauuuulllltttt vvvvaaaalllluuuueeeessss For most platforms, mtools contains reasonable compiled-in defaults. You usually don't need to bother with the configuration file, if all you want to do with mtools is to access your floppy drives. On the other hand, the configuration file is needed if you also want to use mtools to access your hard disk partitions and dosemu image files. GGGGLLLLOOOOBBBBAAAALLLL VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS Global variables may be set to 1 or to 0. The following global flags are recognized: MMMMTTTTOOOOOOOOLLLLSSSS____SSSSKKKKIIIIPPPP____CCCCHHHHEEEECCCCKKKK If this is set to 1, mtools skips most of its sanity Page 1 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) checks. This is needed to read some Atari disks which have been made with the earlier ROMs, and which would not be recognized otherwise. MMMMTTTTOOOOOOOOLLLLSSSS____FFFFAAAATTTT____CCCCOOOOMMMMPPPPAAAATTTTIIIIBBBBIIIILLLLIIIITTTTYYYY If this is set to 1, mtools skips the fat size checks. Some disks have a bigger FAT than they really need to. These are rejected if this option is not set. MMMMTTTTOOOOOOOOLLLLSSSS____LLLLOOOOWWWWEEEERRRR____CCCCAAAASSSSEEEE If this is set to 1, mtools displays all-upper-case short filenames as lowercase. This has been done to allow a behavior which is consistent with older versions of mtools which didn't know about the case bits. Example: Inserting the following line into your configuration file instructs mtools to skip the sanity checks: MMMMTTTTOOOOOOOOLLLLSSSS____SSSSKKKKIIIIPPPP____CCCCHHHHEEEECCCCKKKK====1111 Global variables may also be set via the environment: eeeexxxxppppoooorrrrtttt MMMMTTTTOOOOOOOOLLLLSSSS____SSSSKKKKIIIIPPPP____CCCCHHHHEEEECCCCKKKK====1111 PPPPEEEERRRR DDDDRRRRIIIIVVVVEEEE FFFFLLLLAAAAGGGGSSSS AAAANNNNDDDD VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS Per drive flags and values may be described in a drive section. A drive section starts with ddddrrrriiiivvvveeee _d_r_i_v_e_l_e_t_t_e_r :::: Then follow variable-value pairs and flags. GGGGeeeennnneeeerrrraaaallll PPPPuuuurrrrppppoooosssseeee DDDDrrrriiiivvvveeee VVVVaaaarrrriiiiaaaabbbblllleeeessss The following variables are available: ffffiiiilllleeee The name of the file or device holding the disk image. This is mandatory. The file name should be enclosed in quotes. uuuusssseeee____xxxxddddffff If this is set to a non-zero value, mtools also tries to access this disk as an Xdf disk. Xdf is a high capacity format used by OS/2. This is off by default. ppppaaaarrrrttttiiiittttiiiioooonnnn Tells mtools to treat the drive as a partitioned device, and to use the given partition. Only primary partitions are accessible using this method, and they are numbered from 1 to 4. For logical partitions, use the more general ooooffffffffsssseeeetttt variable. The ppppaaaarrrrttttiiiittttiiiioooonnnn variable is intended for Syquests, ZIP drives, and DOSEMU hdimages. It is not recommended for hard disks to which direct access to partitions is available. ssssccccssssiiii When set to 1, this option tells the operating system Page 2 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) (SunOS or Solaris) that the MS-DOS filesystem exists on an SCSI device (such as a Jaz or a Zip drive). On SunOS/Solaris, these devices can't be accessed using the read and write syscalls, because the OS expects them to contain a Sun specific "disk label". Obviously, Zip and Jaz disks don't contain any such label as they contain PC-style partitions. On Solaris, mtools needs root privileges to be able to use the scsi=1 option. Thus mtools should be installed set uid root on Solaris if you want to access Zip/Jaz drives. Mtools only uses its root privileges when issuing these SCSI ioctl's. The device file and any copied files are still opened with the user's rights. Moreover, mtools drops its root privileges whenever mtools performs "shell expansion" of a device filename contained in its configuration files. For example, if your /etc/mtools.conf file contains a line such as the following, then the scsi=1 option does not work for drive e: drive e: file="$HOME/dosimage" Other drives are not affected: in the following example, the scsi=1 option still works for drive d: drive e: file="$HOME/dosimage" drive d: file="/dev/zip" scsi=1 However, other lines bearing the same drive number are affected: drive e: file="$HOME/dosimage" drive e: file="/dev/zip" scsi=1 ooooffffffffsssseeeetttt Describes where in the file the MSDOS filesystem starts. This is useful for logical partitions in DDDDOOOOSSSSEEEEMMMMUUUU hhhhddddiiiimmmmaaaaggggeeees, and for AAAATTTTAAAARRRRIIII ram disks. By default, this is zero, meaning that the filesystem starts right at the beginning of the device or file. ffffaaaatttt____bbbbiiiittttssss The number of FAT bits. This may be 12 or 16. This is very rarely needed, as it can almost always be deduced from information in the boot sector. On the contrary, describing the number of fat bits may actually be harmful if you get it wrong. You should only use it if Page 3 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) mtools gets the autodetected number of fat bits wrong, or if you want to mformat a disk with a weird number of fat bits. Only the ffffiiiilllleeee option is mandatory. The other parameters may be left out. In that case a default value or an autodetected value is used. DDDDrrrriiiivvvveeee GGGGeeeeoooommmmeeeettttrrrryyyy CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn Geometry information describes the physical characteristics about the disk. Its has three purposes: mmmmffffoooorrrrmmmmaaaatttt The geometry information is written into the boot sector of the newly made disk. However, you may also describe the geometry information on the command line. See mformat(1) for details. ffffiiiilllltttteeeerrrriiiinnnngggg On some Unices there are device nodes which only support one physical geometry. The geometry is compared to the actual geometry stored on the boot sector to make sure that this device node is able to correctly read the disk. If the geometry doesn't match, this drive entry fails, and the next drive entry bearing the same drive letter is tried. See the next section "Supplying multiple descriptions for a drive" for more details on supplying several descriptions for a drive letter. If no geometry information is supplied in the configuration file, all disks are accepted. On Linux (and on Sparc) there exist device nodes with configurable geometry (////ddddeeeevvvv////ffffdddd0000, ////ddddeeeevvvv////ffffdddd1111 etc), and thus filtering is not needed (and ignored) for disk drives. (Mtools still does do filtering on plain files (disk images) in Linux: this is mainly intended for test purposes, as I don't have access to a Unix which would actually need filtering). iiiinnnniiiittttiiiiaaaallll ggggeeeeoooommmmeeeettttrrrryyyy The geometry information (if available) is also used to set the initial geometry on configurable device nodes. This initial geometry is used to read the boot sector, which contains the real geometry. If no geometry information is supplied in the configuration file, no initial configuration is done. On Linux, this is not really needed either, as the configurable devices are able to autodetect the disk type accurately enough (for most common formats) to read the boot sector. Page 4 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) Wrong geometry information may lead to very bizarre errors. That's why I strongly recommend that you don't use geometry configuration unless you really need it. The following geometry related variables are available: ccccyyyylllliiiinnnnddddeeeerrrrssss The number of cylinders. hhhheeeeaaaaddddssss The number of heads (sides). sssseeeeccccttttoooorrrrssss The number of sectors per track. Example: the following drive section describes a 1.44M drive: ddddrrrriiiivvvveeee aaaa:::: ffffiiiilllleeee====""""////ddddeeeevvvv////ffffdddd0000HHHH1111444444440000"""" ffffaaaatttt____bbbbiiiittttssss====11112222 ttttrrrraaaacccckkkkssss====88880000 hhhheeeeaaaaddddssss====2222 sssseeeeccccttttoooorrrrssss====11118888 The following shorthand geometry descriptions are available: 1111....44444444mmmm high density 3 1/2 disk. Equivalent to: ffffaaaatttt____bbbbiiiittttssss====11112222 ttttrrrraaaacccckkkkssss====88880000 hhhheeeeaaaaddddssss====2222 sssseeeeccccttttoooorrrrssss====11118888 1111....2222mmmm high density 5 1/4 disk. Equivalent to: ffffaaaatttt____bbbbiiiittttssss====11112222 ttttrrrraaaacccckkkkssss====88880000 hhhheeeeaaaaddddssss====2222 sssseeeeccccttttoooorrrrssss====11115555 777722220000kkkk double density 3 1/2 disk. Equivalent to: ffffaaaatttt____bbbbiiiittttssss====11112222 ttttrrrraaaacccckkkkssss====88880000 hhhheeeeaaaaddddssss====2222 sssseeeeccccttttoooorrrrssss====9999 333366660000kkkk double density 5 1/4 disk. Equivalent to: ffffaaaatttt____bbbbiiiittttssss====11112222 ttttrrrraaaacccckkkkssss====44440000 hhhheeeeaaaaddddssss====2222 sssseeeeccccttttoooorrrrssss====9999 The shorthand format descriptions may be amended. For example, 333366660000kkkk sssseeeeccccttttoooorrrrssss====8888 describes a 320k disk and is equivalent to: ffffaaaatttt____bbbbiiiittttssss====11112222 ttttrrrraaaacccckkkkssss====44440000 hhhheeeeaaaaddddssss====2222 sssseeeeccccttttoooorrrrssss====8888 OOOOppppeeeennnn FFFFllllaaaaggggssss Moreover, the following flags are available: ssssyyyynnnncccc All i/o operations are done synchronously nnnnooooddddeeeellllaaaayyyy The device or file is opened with the O_NDELAY flag. This is needed on some non-Linux architectures. Page 5 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) eeeexxxxcccclllluuuussssiiiivvvveeee The device or file is opened with the O_EXCL flag. On Linux, this ensures exclusive access to the floppy drive. On most other architectures, and for plain files it has no effect at all. SSSSuuuuppppppppllllyyyyiiiinnnngggg mmmmuuuullllttttiiiipppplllleeee ddddeeeessssccccrrrriiiippppttttiiiioooonnnnssss ffffoooorrrr aaaa ddddrrrriiiivvvveeee It is possible to supply multiple descriptions for a drive. In that case, the descriptions are tried in order until one is found that fits. Descriptions may fail for several reasons: 1111 because the geometry is not appropriate, 2222 because there is no disk in the drive, 3333 or because of other problems. Multiple definitions are useful when using physical devices which are only able to support one single disk geometry. Example: ddddrrrriiiivvvveeee aaaa:::: ffffiiiilllleeee====""""////ddddeeeevvvv////ffffdddd0000HHHH1111444444440000"""" 1111....44444444mmmm ddddrrrriiiivvvveeee aaaa:::: ffffiiiilllleeee====""""////ddddeeeevvvv////ffffdddd0000HHHH777722220000"""" 777722220000kkkk This instructs mtools to use /dev/fd0H1440 for 1.44m (high density) disks and /dev/fd0H720 for 720k (double density) disks. On Linux, this feature is not really needed, as the /dev/fd0 device is able to handle any geometry. You may also use multiple drive descriptions to access both of your physical drives through one drive letter: ddddrrrriiiivvvveeee zzzz:::: ffffiiiilllleeee====""""////ddddeeeevvvv////ffffdddd0000"""" ddddrrrriiiivvvveeee zzzz:::: ffffiiiilllleeee====""""////ddddeeeevvvv////ffffdddd1111"""" With this description, mmmmddddiiiirrrr zzzz:::: accesses your first physical drive if it contains a disk. If the first drive doesn't contain a disk, mtools checks the second drive. When using multiple configuration files, drive descriptions in the files parsed last override descriptions for the same drive in earlier files. In order to avoid this, use the ddddrrrriiiivvvveeee++++ or ++++ddddrrrriiiivvvveeee keywords instead of ddddrrrriiiivvvveeee . The first adds a description to the end of the list (will be tried last), and the first adds it to the start of the list. CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR TTTTRRRRAAAANNNNSSSSLLLLAAAATTTTIIIIOOOONNNN TTTTAAAABBBBLLLLEEEESSSS If you live in the USA, in Western Europe or in Australia, you may skip this section. Page 6 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) IIIInnnnttttrrrroooodddduuuuccccttttiiiioooonnnn DOS uses a different character code mapping than Unix. 7-bit characters still have the same meaning, only characters with the eight bit set are affected. To make matters worse, there are several translation tables available depending on the country where you are. The appearance of the characters is defined using code pages. These code pages aren't the same for all countries. For instance, some code pages don't contain upper case accented characters. On the other hand, some code pages contain characters which don't exist in Unix, such as certain line-drawing characters or accented consonants used by some Eastern European countries. This affects two things, relating to filenames: uuuuppppppppeeeerrrr ccccaaaasssseeee cccchhhhaaaarrrraaaacccctttteeeerrrrssss In short names, only upper case characters are allowed. This also holds for accented characters. For instance, in a code page which doesn't contain accented uppercase characters, the accented lowercase characters get transformed into their unaccented counterparts. lllloooonnnngggg ffffiiiilllleeee nnnnaaaammmmeeeessss Micro$oft has finally come to their senses and uses a more standard mapping for the long file names. They use Unicode, which is basically a 32 bit version of ASCII. Its first 256 characters are identical to Unix ASCII. Thus, the code page also affects the correspondence between the codes used in long names and those used in short names Mtools considers the filenames entered on the command line as having the Unix mapping, and translates the characters to get short names. By default, code page 850 is used with the Swiss uppercase/lowercase mapping. I chose this code page, because its set of existing characters most closely matches Unix's. Moreover, this code page covers most characters in use in the USA, Australia and Western Europe. However, it is still possible to chose a different mapping. There are two methods: the ccccoooouuuunnnnttttrrrryyyy variable and explicit tables. CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn uuuussssiiiinnnngggg CCCCoooouuuunnnnttttrrrryyyy The CCCCOOOOUUUUNNNNTTTTRRRRYYYY variable is recommended for people which also have access to MSDOS system files and documentation. If you don't have access to these, I'd suggest you'd rather use explicit tables instead. Syntax: CCCCOOOOUUUUNNNNTTTTRRRRYYYY====""""_c_o_u_n_t_r_y[[[[,,,,[[[[_c_o_d_e_p_a_g_e]]]],,,,_c_o_u_n_t_r_y._s_y_s]]]]"""" This tells mtools to use a Unix-to-DOS translation table Page 7 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) which matches _c_o_d_e_p_a_g_e and an lowercase-to-uppercase table for _c_o_u_n_t_r_y and to use the _c_o_u_n_t_r_y._s_y_s file to get the lowercase-to-uppercase table. The country code is most often the telephone prefix of the country. Refer to the DOS help page on "country" for more details. The _c_o_d_e_p_a_g_e and the _c_o_u_n_t_r_y._s_y_s parameters are optional. Please don't type in the square brackets, they are only there to say which parameters are optional. The ccccoooouuuunnnnttttrrrryyyy....ssssyyyyssss file is supplied with MSDOS. In most cases you don't need it, as the most common translation tables are compiled into mtools. So, don't worry if you run a Unix-only box which lacks this file. If _c_o_d_e_p_a_g_e is not given, a per country default code page is used. If the _c_o_u_n_t_r_y._s_y_s parameter isn't given, compiled-in defaults are used for the lowercase-to-uppercase table. This is useful for other Unices than Linux, which may have no ccccoooouuuunnnnttttrrrryyyy....ssssyyyyssss file available online. The Unix-to-DOS are not contained in the _c_o_u_n_t_r_y._s_y_s file, and thus mtools always uses compiled-in defaults for those. Thus, only a limited amount of code pages are supported. If your preferred code page is missing, or if you know the name of the Windows 95 file which contains this mapping, could you please drop me a line at aaaallllaaaaiiiinnnn@@@@lllliiiinnnnuuuuxxxx....lllluuuu . The CCCCOOOOUUUUNNNNTTTTRRRRYYYY variable can also be set using the environment. CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn uuuussssiiiinnnngggg eeeexxxxpppplllliiiicccciiiitttt ttttrrrraaaannnnssssllllaaaattttiiiioooonnnn ttttaaaabbbblllleeeessss Translation tables may be described in line in the configuration file. Two tables are needed: first the DOS- to-Unix table, and then the Lowercase-to-Uppercase table. A DOS-to-Unix table starts with the ttttoooouuuunnnniiiixxxx keyword, followed by a colon, and 128 hexadecimal numbers. A lower-to-upper table starts with the ffffuuuuccccaaaasssseeee keyword, followed by a colon, and 128 hexadecimal numbers. The tables only show the translations for characters whose codes is greater than 128, because translation for lower codes is trivial. Example: ttttoooouuuunnnniiiixxxx:::: 0000xxxxcccc7777 0000xxxxffffcccc 0000xxxxeeee9999 0000xxxxeeee2222 0000xxxxeeee4444 0000xxxxeeee0000 0000xxxxeeeeaaaa 0000xxxxeeeebbbb 0000xxxxeeee8888 0000xxxxeeeeffff 0000xxxxeeeeeeee 0000xxxxeeeecccc 0000xxxxcccc9999 0000xxxxeeee6666 0000xxxxcccc6666 0000xxxxffff4444 0000xxxxffff6666 0000xxxxffff2222 0000xxxxffffffff 0000xxxxdddd6666 0000xxxxddddcccc 0000xxxxffff8888 0000xxxxaaaa3333 0000xxxxdddd8888 0000xxxxeeee1111 0000xxxxeeeedddd 0000xxxxffff3333 0000xxxxffffaaaa 0000xxxxffff1111 0000xxxxdddd1111 0000xxxxbbbbffff 0000xxxxaaaaeeee 0000xxxxaaaacccc 0000xxxxbbbbdddd 0000xxxxbbbbcccc 0000xxxxaaaa1111 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxxcccc1111 Page 8 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) 0000xxxxaaaa9999 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxxaaaa2222 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxxffff0000 0000xxxxdddd0000 0000xxxxcccc9999 0000xxxxccccbbbb 0000xxxxcccc8888 0000xxxx66669999 0000xxxxccccffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx5555ffff 0000xxxx7777cccc 0000xxxxdddd3333 0000xxxxddddffff 0000xxxxdddd4444 0000xxxxdddd2222 0000xxxxffff5555 0000xxxxdddd5555 0000xxxxddddeeee 0000xxxxddddaaaa 0000xxxxdddd9999 0000xxxxffffdddd 0000xxxxdddddddd 0000xxxxddddeeee 0000xxxxaaaadddd 0000xxxxbbbb1111 0000xxxx5555ffff 0000xxxxbbbbeeee 0000xxxxbbbb6666 0000xxxxaaaa7777 0000xxxxbbbb0000 0000xxxxaaaa8888 0000xxxxbbbb7777 0000xxxxbbbb9999 0000xxxxbbbb3333 0000xxxxbbbb2222 ffffuuuuccccaaaasssseeee:::: 0000xxxx88880000 0000xxxx9999aaaa 0000xxxx99990000 0000xxxxbbbb6666 0000xxxx8888eeee 0000xxxxbbbb7777 0000xxxxdddd2222 0000xxxxdddd3333 0000xxxxdddd4444 0000xxxxdddd8888 0000xxxxdddd7777 0000xxxxddddeeee 0000xxxx99990000 0000xxxx99992222 0000xxxx99992222 0000xxxxeeee2222 0000xxxx99999999 0000xxxxeeee3333 0000xxxx55559999 0000xxxx99999999 0000xxxx9999aaaa 0000xxxx9999dddd 0000xxxx9999cccc 0000xxxx9999dddd 0000xxxxbbbb5555 0000xxxxdddd6666 0000xxxxeeee0000 0000xxxxeeee9999 0000xxxxaaaa5555 0000xxxxaaaa5555 0000xxxxaaaa8888 0000xxxxaaaa9999 0000xxxxaaaaaaaa 0000xxxxaaaabbbb 0000xxxxaaaacccc 0000xxxxaaaadddd 0000xxxxbbbb0000 0000xxxxbbbb1111 0000xxxxbbbb2222 0000xxxxbbbb3333 0000xxxxbbbb4444 0000xxxxbbbb5555 0000xxxxbbbb8888 0000xxxxbbbb9999 0000xxxxbbbbaaaa 0000xxxxbbbbbbbb 0000xxxxbbbbcccc 0000xxxxbbbbdddd 0000xxxxcccc0000 0000xxxxcccc1111 0000xxxxcccc2222 0000xxxxcccc3333 0000xxxxcccc4444 0000xxxxcccc5555 0000xxxxcccc8888 0000xxxxcccc9999 0000xxxxccccaaaa 0000xxxxccccbbbb 0000xxxxcccccccc 0000xxxxccccdddd 0000xxxxdddd1111 0000xxxxdddd1111 0000xxxxdddd2222 0000xxxxdddd3333 0000xxxxdddd4444 0000xxxx44449999 0000xxxxdddd8888 0000xxxxdddd9999 0000xxxxddddaaaa 0000xxxxddddbbbb 0000xxxxddddcccc 0000xxxxdddddddd 0000xxxxeeee0000 0000xxxxeeee1111 0000xxxxeeee2222 0000xxxxeeee3333 0000xxxxeeee5555 0000xxxxeeee5555 0000xxxxeeee8888 0000xxxxeeee9999 0000xxxxeeeeaaaa 0000xxxxeeeebbbb 0000xxxxeeeedddd 0000xxxxeeeedddd 0000xxxxffff0000 0000xxxxffff1111 0000xxxxffff2222 0000xxxxffff3333 0000xxxxffff4444 0000xxxxffff5555 0000xxxxffff8888 0000xxxxffff9999 0000xxxxffffaaaa 0000xxxxffffbbbb 0000xxxxffffcccc 0000xxxxffffdddd The first table maps DOS character codes to Unix character codes. For example, the DOS character number 129. This is a u with to dots on top of it. To translate it into Unix, we look at the character number 1 in the first table (1 = 129 - 128). This is 0xfc. (Beware, numbering starts at 0). The second table maps lower case DOS characters to upper case DOS characters. The same lower case u with dots maps to character 0x9a, which is an uppercase U with dots in DOS. UUUUnnnniiiiccccooooddddeeee cccchhhhaaaarrrraaaacccctttteeeerrrrssss ggggrrrreeeeaaaatttteeeerrrr tttthhhhaaaannnn 222255556666 If an existing MSDOS name contains Unicode character greater than 256, these are translated to underscores or to characters which are close in visual appearance. For example, accented consonants are translated into their unaccented counterparts. This translation is used for mdir and for the Unix filenames generated by mcopy. Linux does support Unicode too, but unfortunately too few applications support it yet to bother with it in mtools. Most importantly, xterm can't display Unicode yet. If there is sufficient demand, I might include support for Unicode in the Unix filenames as well. CCCCaaaauuuuttttiiiioooonnnn:::: When deleting files with mtools, the underscore Page 9 (printed 7/15/98) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccc 5555,,,, 1111999999995555)))) MMMMTTTTOOOOOOOOLLLLSSSS((((5555)))) matches all characters which can't be represented in Unix. Be careful before mdel! LLLLOOOOCCCCAAAATTTTIIIIOOOONNNN OOOOFFFF CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN FFFFIIIILLLLEEEESSSS AAAANNNNDDDD PPPPAAAARRRRSSSSIIIINNNNGGGG The configuration files are parsed in the following order: 1111 compiled-in defaults 2222 ////eeeettttcccc////mmmmttttoooooooollllssss....ccccoooonnnnffff 3333 ////eeeettttcccc////mmmmttttoooooooollllssss This is for backwards compatibility only, and is only parsed if mmmmttttoooooooollllssss....ccccoooonnnnffff doesn't exist. 4444 ~~~~////....mmmmttttoooooooollllssssrrrrcccc. Options described in the later files override those described in the earlier files. Drives defined in earlier files persist if they are not overridden in the later files. For instance, drives A and B may be defined in ////eeeettttcccc////mmmmttttoooooooollllssss....ccccoooonnnnffff and drives C and D may be defined in ~~~~////....mmmmttttoooooooollllssssrrrrcccc However, if ~~~~////....mmmmttttoooooooollllssssrrrrcccc also defines drive A, this new description would override the description of drive A in ////eeeettttcccc////mmmmttttoooooooollllssss....ccccoooonnnnffff instead of adding to it. If you want to add a new description to a drive already described in an earlier file, you need to use either the ++++ddddrrrriiiivvvveeee or ddddrrrriiiivvvveeee++++ keyword. BBBBAAAACCCCKKKKWWWWAAAARRRRDDDDSSSS CCCCOOOOMMMMPPPPAAAATTTTIIIIBBBBIIIILLLLIIIITTTTYYYY The syntax described herein is new for version mmmmttttoooooooollllssss----2222....5555....4444. The old line-oriented syntax is still supported. Each line beginning with a single letter is considered to be a drive description using the old syntax. Old style and new style drive sections may be mixed within the same configuration file, in order to make upgrading easier. Support for the old syntax will be phased out eventually, and in order to discourage its use, I purposefully omit its description here. FFFFIIIILLLLEEEESSSS /etc/mtools.conf, ~/.mtoolsrc SSSSEEEEEEEE AAAALLLLSSSSOOOO _m_t_o_o_l_s(1) Page 10 (printed 7/15/98)